InfoMagic Internet Tools 1995 April/Internet Tools.iso/dos_win/winsock/maillist/94-03.Z/94-03/text0059.txt

Text File | 1994-03-30 | 7.0 KB | 166 lines

>In article <2l6lf1$[e-mail]> [e-mail] (Glen Daniels)
>writes:
>>Hi, all!
>[stuff deleted]
>>       *** PLEASE NOTE FILENAME CHANGE! ***
>>
>>       The executable is now called WTALK11.EXE.  Sorry for the name
>>change, but I hope you'll agree it's a much better policy to include
>>version information in the filenames.  Your old progman icons WILL
>>NEED TO BE CHANGED to reflect the new .exe name.
>[more stuff deleted]

>Personally I strongly dislike this 'policy to include version information in the
>filenames',
>except for the zip-file of course. The main reason for my opinion is given by
>Glen Daniels himself:
>'Your old progman icons WILL NEED TO BE CHANGED to reflect the new .exe name.'
>As often as these programs
>are released in new versions you'll get a 'lot of work' editing various settings
>if the filename itself
>is changed every time. An other reason is the somewhat cryptic names you could
>end up with,
>e.g. tw10b_b1.exe (it should be trumpet winsock ver 1.0 rev B beta # 1) who the
>... would remember such names?
>In cases like this I always change the filename, removing any indication of
>version number! (And hoping that
>I'm not violating any copyright laws.)

>The version number should easyly be found in About ... within the program. If
>one want to state the version number
>without starting the program, it could be included in the icon, like adobe type
>manager does.

>Anyone (dis)agree?

I strongly agree with NOT changing the file name.  I manage a largish network
and would need to change the name on MANY windows.

If all programs would do this I would have time to do nothing but change icons.




    *********************************************************************
    *  Thomas D. Gasser                                                 *
    *  Department of Neurosurgery                *******     ******     *
    *  University of Minnesota                    ***  *** *** ***      *
    *  [phone]                             ***   *****  ***      *
    *  E-Mail:  [e-mail]         *****        *****     *
    *                                                                   *
    *********************************************************************
From [e-mail] Fri Mar  4 19:07:00 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA04676; Fri, 4 Mar 1994 15:29:27 -0500
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA29436; Fri, 4 Mar 1994 15:02:01 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: 4 Mar 1994 19:07:00 GMT
From: [e-mail] (Tex)
Message-Id: <[e-mail]>
Organization: Foobar inc.
Sender: ses
References: <2l7jmv$[e-mail]>
Subject: Re: Mosaic and PPP under Windows.

In article <2l7jmv$[e-mail]>, [e-mail] (Maldoror 2) says:
>
>I am currently trying to set up my laptop so I can dial in to a PPP provider
>and use Mosaic.  Trumpet Winsock only supports SLIP, so does anyone know of a
>way that I can get connected?
>P.S. I'm a novice, so please keep it simple.
>
>Thanks in advance
>
>[e-mail]


Experimentally I found the following works

    1.) Connect using your PPP software (usually STARTPPP)

    2.) Load the Winpkt driver (protected mode Packet Driver)

    3.) Run TCPMAN and tell it to use bootp for your IP address
        it's under setup

        4.) Run your favorite winsock applications


From [e-mail] Fri Mar  4 19:42:45 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA04692; Fri, 4 Mar 1994 15:29:29 -0500
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA15852; Fri, 4 Mar 1994 15:24:26 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: Fri, 4 Mar 1994 19:42:45 GMT
From: [e-mail] (Pat J. Pinchera)
Message-Id: <[e-mail]>
Organization: ICS, Melbourne FL
Sender: ses
Subject: Synchronous Serial

How do I reconfigure the Zilog 8530 serial controller to operate
in synchronous mode? (i.e. utilize clock pin) This must be compatible
with SunOS 4.1.3.  If anyone has any information about this, or can
refer me to some information source, it would be greatly appreciated.
Reply here or e-mail. I'll check both. Posted for a co-worker.

Pat
--
Patrick Pinchera                     [e-mail]
ICS               "If I knew art smelled this good, I would've come here years
Melbourne, FL      ago."   Melanie Griffith as Billie Dawn in _Born_Yesterday_
From [e-mail] Fri Mar  4 05:18:41 1994
Received: from halon.sybase.com by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA11804; Fri, 4 Mar 1994 16:19:01 -0500
Received: from sybase.com (sybgate.sybase.com) by halon.sybase.com (5.0/SMI-SVR4/SybFW4.0)
    id AA04581; Fri, 4 Mar 94 13:21:23 PST
Received: from pokey.sybgate.sybase.com by sybase.com (4.1/SMI-4.1/SybH3.3)
    id AA16851; Fri, 4 Mar 94 13:18:44 PST
Received: by pokey.sybgate.sybase.com (4.1/SMI-4.1/SybEC3.2)
    id AA01511; Fri, 4 Mar 94 13:18:42 PST
From: [e-mail] (Not A Babe)
Message-Id: <[e-mail]>
Subject: Re: problem with winsock.lib
To: [e-mail] (Insitu Inc.)
Date: Fri, 4 Mar 94 13:18:41 PST
Cc: [e-mail]
In-Reply-To: <[e-mail]>; from "Insitu Inc." at Mar 3, 94 9:31 pm
X-Mailer: ELM [version 2.3 PL0]
Content-Length: 1471

> Can someone help me, I'm sure there's a simple solution to this behaviour.
>
> When I build my winsock application I link in the winsock.lib file. When the application starts, if it cannot find a winsock.dll anywhere in the path then it bombs out with a system modal "Cannot find WINSOCK.DLL" and the application never
> starts. This message occurs before my applcaition starts and reaches the point
> where I call WSAStartUp to test for a valid WINSOCK.DL
>
> If none is found I handle that error correctly, but of course I can't test this since the app
> never starts.
>

Yup.  winsock.lib is an import library and as such just a list of
DLL entry points.  I believe that Windows controls what's happening.
When you link your app with any import lib, the linker makes a note
that the corresponding DLL must be available at run time.  If the
DLL isn't available at runtime, then Windows won't start your app.

Using LoadLibrary() to load a DLL is an alternative to linking
with a DLL's import library.  If you want to dynamically load
WINSOCK.DLL then you would use LoadLibrary() and you would not
link with winsock.lib.  In this case, your app could handle the
failure of LoadLibrary().  Your app would then be required to
get the function ptrs to the entry points in WINSOCK.DLL using
GetProcAddress().

Rhoda Neimand    [e-mail]    [I speak for myself]
"I would gladly risk feeling bad at times if it meant
I could taste my dessert"        - Data in Hero Worship